home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.misc
- Path: EU.net!sun4nl!hguijt
- From: hguijt@inter.NL.net (Hans Guijt)
- Subject: Re: OS features
- Message-ID: <DLAA61.2us@inter.NL.net>
- Organization: NLnet
- X-Newsreader: TIN [version 1.2 PL2]
- Date: Tue, 16 Jan 1996 17:05:59 GMT
-
-
- >Maybe not 99% but surely the majority. BTW, the Disable() macro has to
- >fail at some point. You cannot get stable operation without absolutely
- >blocking hardware access to normal programs (and.. I would even block
- >Disable() and maybe even Forbid() in the future, same goes to a large
- >variety of system calls that can crash the system and are not needed
- >in normal programs).
-
- Isn't that overly paranoid? I know how much you hate c0derz, but Forbid ()
- has a real purpose (at least in existing machines).
-
- What other functions do you mean here? Keep in mind that not everybody is in
- the business of writing 'normal' programs. Some people need more, and so far
- I think the Amiga catered well to them.
-
- >>The current messaging system can be left unmodified, provided that the
- >>receiving task doesn't modify the message data.
- >
- >Unfortunately it does. A message contains a node that is modified by
- >the PutMsg(), ReplyMsg() and GetMsg() functions.
-
- An 68000 emulator could run without memory protection, and new programs
- should use the MEMF_PUBLIC flag which indicates memory is to be shared
- between applications. I don't see any problem here.
-
-
- Bye,
-
- Hans
-
-